5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
- Chapter 4-9: Appx Chart Director API

Chapter 4-9: Appx Chart Director API

Rendering a Chart


After you have initialized your chart, provided the data to plot and set any other desired attributes, you render the chart by calling the .CHART RENDER routine. This requires just one argument, a field to contain the name of the generated graphic file. The routine will then invoke Chart Director, which will create the graphic file. You can also pass a file name, in which case it will create that file in the default chart directory. If you pass a complete path and file name, the chart will be rendered to that location. If you pass a blank field, the API will assign a unique name for you, using the settings in the parameter file.

If you have standard colors or other attributes that should be the same across all charts, you can create your own subroutine that sets all these attributes before calling .CHART RENDER. In your applications, you would call this subroutine instead of calling .CHART RENDER directly. This would give all your charts a common look and feel.

To use the chart in an input or output process, place an alpha field on your image, drag it out to the appropriate size, and set the GUI attributes to PICTURE, Location Type of SERVER, Position to EXPAND PROP'L and check the Transparent flag. You can then pass this field to the .CHART RENDER routine, and Appx will display the completed chart on your image. Make sure the alpha field is long enough to contain the complete path and file name.

The rendered chart file is not automatically removed, it is your responsbility to clean up any chart files that are no longer needed. The End of Process Event point (for both Inputs and Outputs) is a logical choice, if you are only rendering one chart in the process. If you are rendering more than one chart in the process, you will have to use another technique.

Application Design Manual                                         "Powered by Appx Software"

1270

©2006 By APPX Software, Inc. All Rights Reserved